15.2 AT^SRSM Remote SIM Access MessageThe AT^SRSM command is used to transfer SAP messages between devices acting as SAP server and client. It is applicable for XSAP data format only, for details please refer to the <dataForm> parameter of the AT^SRSA command. The write command transports SAP messages to an SAP server or SAP client.
<RsaDevId>(num)
<RsaMsgId>(num)For details refer to Section 15.2.1, SAP Request Message Parameters and Section 15.2.2, SAP Response Message Parameters.
<RsaMsgData>(str)For details refer to Section 15.2.1, SAP Request Message Parameters and Section 15.2.2, SAP Response Message Parameters.
<RsaMsgLen>(num)For details refer to Section 15.2.1, SAP Request Message Parameters and Section 15.2.2, SAP Response Message Parameters.
<RsaMsgRc>(num)For details refer to Section 15.2.1, SAP Request Message Parameters and Section 15.2.2, SAP Response Message Parameters.
<MaxMsgSize>(num)
• If the TC65 is acting as SAP client the requested value of <MaxMsgSize> is 300. During SAP connection setup this value may be negotiated with the server to the minimal value 274, which is calculated by 256 data bytes as part of a TRANSFER_APDU_RESP message plus a 16 byte SAP header and two status bytes. If the server does not accept this value range no SAP connection will be established.
• If the TC65 is acting as SAP server it requires that a <MaxMsgSize> value of 276 will be accepted by a connected client.
<ConnStatus>(num)
<DiscType>(num)
<CmdApdu>(str)
<CmdApduLen>(num)
<RspApdu>(str)
<RspApduLen>(num)
<ATR>(str)
<AtrLen>(num)
<ResCode>(num)
<CardRdStatus>(num)
<StatusChange>(num)
<TransportProtocol>(num)
Switch on immediate indication of OK response after dialing with ATD. Does the ME support RSA and is a SAP connection established? ME now starts sending SAP message CONNECTION_REQ on dedicated RSA channel. URC indicating the deregistration from network because of loss of SIM.
|